frontend/src/pages/CaseDetail.jsx (1)

68-78: Nice consolidation.

Centralizing the activity-log refresh into refetchActivityLog() removes the duplicated getLogsByRecord + setTimeline plumbing from each mutation handler, and the prev.filter(i => i.type !== 'ACTIVITY') approach correctly preserves locally-appended COMMENT entries added optimistically in handleSendMessage.

One optional hardening: if the user navigates away (caseData.id changes) while a refetch is in flight, the late setTimeline could write logs for the previous record into the new view. A simple guard is to capture the id and bail out on mismatch:

Optional: ignore stale in-flight responses after caseData.id changes

     const refetchActivityLog = async () => {
+        const requestedId = caseData.id;
         try {
-            const logsRes = await activityService.getLogsByRecord(caseData.id);
+            const logsRes = await activityService.getLogsByRecord(requestedId);
+            if (requestedId !== caseData.id) return;
             setTimeline(prev => [
                 ...prev.filter(i => i.type !== 'ACTIVITY'),
                 ...logsRes.data.map(l => ({ ...l, type: 'ACTIVITY' }))
             ].sort((a, b) => new Date(b.createdAt) - new Date(a.createdAt)));
         } catch (error) {
             console.error("Kunde inte uppdatera aktivitetsloggen:", error);
         }
     };

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@frontend/src/pages/CaseDetail.jsx` around lines 68 - 78, refetchActivityLog
can race with navigation: capture the current case id at the start (const
currentId = caseData.id) and before calling setTimeline validate that
caseData.id === currentId; if not, return early to avoid writing logs for a
stale case. Update the refetchActivityLog function (and any callers like
handleSendMessage that rely on it) to perform this guard using the captured id
before merging logs via setTimeline so late responses don't overwrite the
timeline for a newly-selected case.

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes